Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc7faeb0be3ffaa33988e5a78283f886999016669943cfb01cf5d5c1d985f226

Tx prefix hash: 3fbdfa2b1b91c7580bb645af7aebb271f5204bade8946153d8b040df36ebfca1
Tx public key: 8b07291adfd180ab28661283958c7e00adc94101641da2f4f04e077b531f48af
Timestamp: 1578800177 Timestamp [UCT]: 2020-01-12 03:36:17 Age [y:d:h:m:s]: 04:319:21:45:47
Block: 43613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118174 RingCT/type: yes/0
Extra: 018b07291adfd180ab28661283958c7e00adc94101641da2f4f04e077b531f48af0211000000064ac5aa02000000000000000000

1 output(s) for total of 440.050252144000 dcy

stealth address amount amount idx
00: a5403a2c6cf1356ca1d249582a891823c584bfe5d00ab7624904cdaa26beb6e6 440.050252144000 79068 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": 43623, "vin": [ { "gen": { "height": 43613 } } ], "vout": [ { "amount": 440050252144, "target": { "key": "a5403a2c6cf1356ca1d249582a891823c584bfe5d00ab7624904cdaa26beb6e6" } } ], "extra": [ 1, 139, 7, 41, 26, 223, 209, 128, 171, 40, 102, 18, 131, 149, 140, 126, 0, 173, 201, 65, 1, 100, 29, 162, 244, 240, 78, 7, 123, 83, 31, 72, 175, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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