Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4feb10ea4f62b8e22a0b050384dfa3d61ae2779f6cba4bf861123ff394f94d0

Tx prefix hash: 578cb218978a314077e2ce73129527d2721b980ccbb899916bd60345f6e0b73e
Tx public key: 3088c15647f2a7543c84b2e798caf803154b0a3e5946facfa35f23f4edd18d71
Timestamp: 1699613534 Timestamp [UCT]: 2023-11-10 10:52:14 Age [y:d:h:m:s]: 01:074:19:56:55
Block: 888547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314855 RingCT/type: yes/0
Extra: 013088c15647f2a7543c84b2e798caf803154b0a3e5946facfa35f23f4edd18d71021100000004faf35c9c000000000000000000

1 output(s) for total of 0.698031362000 dcy

stealth address amount amount idx
00: 835549504c3d2326b05a26a0031498e1ee3c3de466a513fd180494b7aa6c6464 0.698031362000 1344494 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": 888557, "vin": [ { "gen": { "height": 888547 } } ], "vout": [ { "amount": 698031362, "target": { "key": "835549504c3d2326b05a26a0031498e1ee3c3de466a513fd180494b7aa6c6464" } } ], "extra": [ 1, 48, 136, 193, 86, 71, 242, 167, 84, 60, 132, 178, 231, 152, 202, 248, 3, 21, 75, 10, 62, 89, 70, 250, 207, 163, 95, 35, 244, 237, 209, 141, 113, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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