Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36e5f4e50a1eca83fd70ed9fe8bec54e517971c410a43bdc5211a0d57d2a26a

Tx prefix hash: 8977d37de1aab3f22f1473ac94cefbd2581a918853c2b55d455ff97af50a2cb1
Tx public key: e00d8ae19f55325e41f9aca2f7cfa90aafd274c17c22ca8732271ac8170f3343
Timestamp: 1729522586 Timestamp [UCT]: 2024-10-21 14:56:26 Age [y:d:h:m:s]: 00:238:20:02:51
Block: 1136465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170443 RingCT/type: yes/0
Extra: 01e00d8ae19f55325e41f9aca2f7cfa90aafd274c17c22ca8732271ac8170f3343021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e14bc46345d6cc4c2d37b646214d0949d779b5f47c3bf5300d699616b39174e 0.600000000000 1619810 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": 1136475, "vin": [ { "gen": { "height": 1136465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e14bc46345d6cc4c2d37b646214d0949d779b5f47c3bf5300d699616b39174e" } } ], "extra": [ 1, 224, 13, 138, 225, 159, 85, 50, 94, 65, 249, 172, 162, 247, 207, 169, 10, 175, 210, 116, 193, 124, 34, 202, 135, 50, 39, 26, 200, 23, 15, 51, 67, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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