Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540e74998a0e7b0fea2911e9859dd4f473c45e2df1b715cd347173ed0b35ac4e

Tx prefix hash: 384c7d67cc0f7e622788dde798f2fcbd71fffd1f3c07e78811e79a20be607e6b
Tx public key: 011eba3c88fc680a50ed44d4304364ecf00e90b415c1e15816d528bc45c4c02c
Timestamp: 1717059296 Timestamp [UCT]: 2024-05-30 08:54:56 Age [y:d:h:m:s]: 00:315:03:45:55
Block: 1033171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225251 RingCT/type: yes/0
Extra: 01011eba3c88fc680a50ed44d4304364ecf00e90b415c1e15816d528bc45c4c02c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37868654d83b753eb0319beaf6f93cb4a405b7ae0bb39bfacfaee0a289a088cc 0.600000000000 1501634 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": 1033181, "vin": [ { "gen": { "height": 1033171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37868654d83b753eb0319beaf6f93cb4a405b7ae0bb39bfacfaee0a289a088cc" } } ], "extra": [ 1, 1, 30, 186, 60, 136, 252, 104, 10, 80, 237, 68, 212, 48, 67, 100, 236, 240, 14, 144, 180, 21, 193, 225, 88, 22, 213, 40, 188, 69, 196, 192, 44, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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