Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c552680fe57f966da577fd0d53a23d338a7bc30166986e1b5803d9e1ff3e0ef4

Tx prefix hash: aed3383f787a7318731a611f248ba273d2cb08c800c3b9b933507a591c047eed
Tx public key: d15602219a1ae70b65bb8b8a97ca6c58ce423e8b2933c4515f2c4039a6402d58
Timestamp: 1741284006 Timestamp [UCT]: 2025-03-06 18:00:06 Age [y:d:h:m:s]: 00:005:23:25:00
Block: 1233549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4285 RingCT/type: yes/0
Extra: 01d15602219a1ae70b65bb8b8a97ca6c58ce423e8b2933c4515f2c4039a6402d58021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4041d5dba926d5aef04d0e945e222f10da1e5c3dfa9781304e6d40e8090d26d 0.600000000000 1720472 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": 1233559, "vin": [ { "gen": { "height": 1233549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4041d5dba926d5aef04d0e945e222f10da1e5c3dfa9781304e6d40e8090d26d" } } ], "extra": [ 1, 209, 86, 2, 33, 154, 26, 231, 11, 101, 187, 139, 138, 151, 202, 108, 88, 206, 66, 62, 139, 41, 51, 196, 81, 95, 44, 64, 57, 166, 64, 45, 88, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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