Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e98eaca43ee50676b011f4843b7d4466df425475f127facf8e5d7e03c89d7e63

Tx prefix hash: 02075b86b0751d673e952e202a1d5108159be6b6eae3e9a993f345d6730b2bc1
Tx public key: e5bf91154e97df76f9e8cfa336883463b044baeeffafd0883a85bc9906e14c7b
Timestamp: 1714278429 Timestamp [UCT]: 2024-04-28 04:27:09 Age [y:d:h:m:s]: 00:251:19:40:22
Block: 1010117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180258 RingCT/type: yes/0
Extra: 01e5bf91154e97df76f9e8cfa336883463b044baeeffafd0883a85bc9906e14c7b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aba32f72f9151354becfcee22da090c9f2bade3a3b3c5bfe75cb1f5a6d64dbe0 0.600000000000 1471981 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": 1010127, "vin": [ { "gen": { "height": 1010117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aba32f72f9151354becfcee22da090c9f2bade3a3b3c5bfe75cb1f5a6d64dbe0" } } ], "extra": [ 1, 229, 191, 145, 21, 78, 151, 223, 118, 249, 232, 207, 163, 54, 136, 52, 99, 176, 68, 186, 238, 255, 175, 208, 136, 58, 133, 188, 153, 6, 225, 76, 123, 2, 17, 0, 0, 0, 2, 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