Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404ae58bf1ad1d51c2e3e1bee034893e26dfc1f85862715ab69c9ac3046961d5

Tx prefix hash: 302f2e2af385bca766aa7ee0d33d76e17162ae3c167efdc2b89e5505b0a22d70
Tx public key: 57b7fadc4a2fddd6577aa76d7256e2d07f31bb6df8f5470933e0ce8f4b12db38
Timestamp: 1635627036 Timestamp [UCT]: 2021-10-30 20:50:36 Age [y:d:h:m:s]: 03:179:02:57:07
Block: 363865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 906333 RingCT/type: yes/0
Extra: 0157b7fadc4a2fddd6577aa76d7256e2d07f31bb6df8f5470933e0ce8f4b12db3802110000000b745f00f8000000000000000000

1 output(s) for total of 38.226506574000 dcy

stealth address amount amount idx
00: 42db2310334f76bea9ea983dde9e8c218236f2a2ba0de5b5d7935a2524279ce4 38.226506574000 739395 of 0

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": 363875, "vin": [ { "gen": { "height": 363865 } } ], "vout": [ { "amount": 38226506574, "target": { "key": "42db2310334f76bea9ea983dde9e8c218236f2a2ba0de5b5d7935a2524279ce4" } } ], "extra": [ 1, 87, 183, 250, 220, 74, 47, 221, 214, 87, 122, 167, 109, 114, 86, 226, 208, 127, 49, 187, 109, 248, 245, 71, 9, 51, 224, 206, 143, 75, 18, 219, 56, 2, 17, 0, 0, 0, 11, 116, 95, 0, 248, 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