Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9890d6d4926848a3b5ee663dd18517bf80b20a2c27d2e3e0fe326859970527be

Tx prefix hash: aa046bc3ffd4b6fb06d02149d4270121f2316a1d63c712b24f928c85004c0934
Tx public key: 45f910f37b935073ad808a1e41ccd833cda11250c2d7b08978ee55d0a954d70b
Timestamp: 1710357239 Timestamp [UCT]: 2024-03-13 19:13:59 Age [y:d:h:m:s]: 01:026:16:35:33
Block: 977635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280053 RingCT/type: yes/0
Extra: 0145f910f37b935073ad808a1e41ccd833cda11250c2d7b08978ee55d0a954d70b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4166145357f0161f1c62e5fafc4041b25a1e7a62739af3c197ce178f709ac8b3 0.600000000000 1437638 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": 977645, "vin": [ { "gen": { "height": 977635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4166145357f0161f1c62e5fafc4041b25a1e7a62739af3c197ce178f709ac8b3" } } ], "extra": [ 1, 69, 249, 16, 243, 123, 147, 80, 115, 173, 128, 138, 30, 65, 204, 216, 51, 205, 161, 18, 80, 194, 215, 176, 137, 120, 238, 85, 208, 169, 84, 215, 11, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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