Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 39240fcad50c52cfec60733853977d9c0d9424b8b0f790169bcbbb5308b9c63f

Tx prefix hash: a61a10b7522275a0d2b1f5630c4ec158c573a07c1de3971685c64b31615b3747
Tx public key: 880acb1b5f2d1ee8958d881ea3d51b87d07b45ee0892e86004cf0bdf77817e23
Timestamp: 1745295370 Timestamp [UCT]: 2025-04-22 04:16:10 Age [y:d:h:m:s]: 00:213:21:47:17
Block: 1266745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150605 RingCT/type: yes/0
Extra: 01880acb1b5f2d1ee8958d881ea3d51b87d07b45ee0892e86004cf0bdf77817e230211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 715e1799a8410a2fd1798f582d44c94b7f814cd39a2d36d9d8eb5a8a100552f3 0.600000000000 1753966 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1266755, "vin": [ { "gen": { "height": 1266745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "715e1799a8410a2fd1798f582d44c94b7f814cd39a2d36d9d8eb5a8a100552f3" } } ], "extra": [ 1, 136, 10, 203, 27, 95, 45, 30, 232, 149, 141, 136, 30, 163, 213, 27, 135, 208, 123, 69, 238, 8, 146, 232, 96, 4, 207, 11, 223, 119, 129, 126, 35, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8