Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3bfe38158391b862bfc2d46cae0f37d2f81c734309c04c629116ae32bab7843

Tx prefix hash: a1d482d7d1f84f4c1629555ee2b425d74ec2d03031434beaf2990f6683a9f2a3
Tx public key: cebfcdca9061e0eee83094878f2432fd61a53386d2263d9649ca7c131883d1f4
Timestamp: 1731290152 Timestamp [UCT]: 2024-11-11 01:55:52 Age [y:d:h:m:s]: 00:193:21:28:27
Block: 1151074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138431 RingCT/type: yes/0
Extra: 01cebfcdca9061e0eee83094878f2432fd61a53386d2263d9649ca7c131883d1f40211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43f32e728fd7d5868e7093f65d6d182c02ebd75030caf0d595b0eb9f733fe690 0.600000000000 1636531 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": 1151084, "vin": [ { "gen": { "height": 1151074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43f32e728fd7d5868e7093f65d6d182c02ebd75030caf0d595b0eb9f733fe690" } } ], "extra": [ 1, 206, 191, 205, 202, 144, 97, 224, 238, 232, 48, 148, 135, 143, 36, 50, 253, 97, 165, 51, 134, 210, 38, 61, 150, 73, 202, 124, 19, 24, 131, 209, 244, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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