Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce0f9db12be5a70267b3811b49b506f2bdd1c3be308bd1b2587011fd94272c14

Tx prefix hash: e93181d986fb6c315ba6eb04af4242901b65970af9a2c70f358b4f78386af676
Tx public key: f54e3d3c994040d0fdaba9bd133b884ec2dd8f72acea89aea0024f127326c8c4
Timestamp: 1725273357 Timestamp [UCT]: 2024-09-02 10:35:57 Age [y:d:h:m:s]: 00:203:09:49:14
Block: 1101272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145213 RingCT/type: yes/0
Extra: 01f54e3d3c994040d0fdaba9bd133b884ec2dd8f72acea89aea0024f127326c8c4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23227f547347aa144cc0ae8ddcbc5349747a7d76d9e1040fb0346cce028f213c 0.600000000000 1577259 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": 1101282, "vin": [ { "gen": { "height": 1101272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23227f547347aa144cc0ae8ddcbc5349747a7d76d9e1040fb0346cce028f213c" } } ], "extra": [ 1, 245, 78, 61, 60, 153, 64, 64, 208, 253, 171, 169, 189, 19, 59, 136, 78, 194, 221, 143, 114, 172, 234, 137, 174, 160, 2, 79, 18, 115, 38, 200, 196, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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