Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7b01979b0617d4374571946041502d1ec95e7f045e2f2cfa78d801931e0128

Tx prefix hash: d49b58aa1b9353a88d4b587bf3d3fd5ba1ef52089a65aeb0fbd2c82bc93ffac8
Tx public key: 9278fe0aed86138f1cf363384d3b2e479d387b751f5e30e2303a333881e54401
Timestamp: 1710559383 Timestamp [UTC]: 2024-03-16 03:23:03 Age [y:d:h:m:s]: 02:062:22:10:45
Block: 979304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557001 RingCT/type: yes/0
Extra: 019278fe0aed86138f1cf363384d3b2e479d387b751f5e30e2303a333881e544010211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d2f29ec2359396f48a680530c954515fdcb585d9ebb03dd5ec2eaf9b7afc4854 0.000600000000 1439337 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 dinastycoin-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": 979314, "vin": [ { "gen": { "height": 979304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2f29ec2359396f48a680530c954515fdcb585d9ebb03dd5ec2eaf9b7afc4854" } } ], "extra": [ 1, 146, 120, 254, 10, 237, 134, 19, 143, 28, 243, 99, 56, 77, 59, 46, 71, 157, 56, 123, 117, 31, 94, 48, 226, 48, 58, 51, 56, 129, 229, 68, 1, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: