Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd29def044ebaf7b3a4fea113ae7f9e3793babc01c53a49021009929112066e2

Tx prefix hash: c4e221a2cb85c2ce50010a3a00a716efd24f17d2e87b136c4e422758a2e85ccf
Tx public key: 553e289e297fb5d5f5827e3ee0a1df0c1bf6f73de90e7d220a5da870c60bab5d
Timestamp: 1648059526 Timestamp [UCT]: 2022-03-23 18:18:46 Age [y:d:h:m:s]: 02:326:22:42:10
Block: 464849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 752943 RingCT/type: yes/0
Extra: 01553e289e297fb5d5f5827e3ee0a1df0c1bf6f73de90e7d220a5da870c60bab5d02110000000ecb8520c2000000000000000000

1 output(s) for total of 17.691414260000 dcy

stealth address amount amount idx
00: a606cf9a5d58c098ae981b8a4b5caf64f8123ac4106af7026c3e6ebc9f39b029 17.691414260000 882826 of 0

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": 464859, "vin": [ { "gen": { "height": 464849 } } ], "vout": [ { "amount": 17691414260, "target": { "key": "a606cf9a5d58c098ae981b8a4b5caf64f8123ac4106af7026c3e6ebc9f39b029" } } ], "extra": [ 1, 85, 62, 40, 158, 41, 127, 181, 213, 245, 130, 126, 62, 224, 161, 223, 12, 27, 246, 247, 61, 233, 14, 125, 34, 10, 93, 168, 112, 198, 11, 171, 93, 2, 17, 0, 0, 0, 14, 203, 133, 32, 194, 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