Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e55e705abbb791688dd0ad195b2067a5ae303254acd584b3d0c80f897de5101

Tx prefix hash: a9fd037c4a4a5ef4de33ca0be91a705396f963d5885340f56714e8fc4ec03b86
Tx public key: 5312507f348cfa3538ff84e5fc336b082f26c99813a9fcb463f2feec87c83c0c
Timestamp: 1733877964 Timestamp [UCT]: 2024-12-11 00:46:04 Age [y:d:h:m:s]: 00:104:10:48:42
Block: 1172520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74422 RingCT/type: yes/0
Extra: 015312507f348cfa3538ff84e5fc336b082f26c99813a9fcb463f2feec87c83c0c0211000000016e963a0b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f2c79b37c3a3f1de1b860f73187a1c539d13f2ceb16aedc68119bf862560af 0.600000000000 1658423 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": 1172530, "vin": [ { "gen": { "height": 1172520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f2c79b37c3a3f1de1b860f73187a1c539d13f2ceb16aedc68119bf862560af" } } ], "extra": [ 1, 83, 18, 80, 127, 52, 140, 250, 53, 56, 255, 132, 229, 252, 51, 107, 8, 47, 38, 201, 152, 19, 169, 252, 180, 99, 242, 254, 236, 135, 200, 60, 12, 2, 17, 0, 0, 0, 1, 110, 150, 58, 11, 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