Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4139f3e52687c9fc87716e3110ee4fe094b52243ea06714d125bf712981a07f

Tx prefix hash: 00263b3633137d0729a5c7e4cba7469f1a6ddc6c72853aee8419db7e69cb2614
Tx public key: 350e52e5ba293e11b353189d00b6cbf35e9e71e58744dee89dfe29dde63c5dad
Timestamp: 1731210887 Timestamp [UCT]: 2024-11-10 03:54:47 Age [y:d:h:m:s]: 00:131:14:03:23
Block: 1150419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93860 RingCT/type: yes/0
Extra: 01350e52e5ba293e11b353189d00b6cbf35e9e71e58744dee89dfe29dde63c5dad021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b1a5a33d06ad6e9a243551553d613e18850b93ae226f2e2500dd2e6e9be814b 0.600000000000 1635728 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": 1150429, "vin": [ { "gen": { "height": 1150419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b1a5a33d06ad6e9a243551553d613e18850b93ae226f2e2500dd2e6e9be814b" } } ], "extra": [ 1, 53, 14, 82, 229, 186, 41, 62, 17, 179, 83, 24, 157, 0, 182, 203, 243, 94, 158, 113, 229, 135, 68, 222, 232, 157, 254, 41, 221, 230, 60, 93, 173, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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