Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0fc94c86d4fb7a4edec0dcf9fb942a4e7f95751cf53a03344a6c8beca989cd4

Tx prefix hash: bba6e4e35973ab622429c92fbd1c5ff8522b7302d580d2bca70e6d865592f8e6
Tx public key: 474f6a6794d663b51fd1a6a873b151d8cda3544842e1204bbb765cce367bd6ce
Timestamp: 1578911655 Timestamp [UCT]: 2020-01-13 10:34:15 Age [y:d:h:m:s]: 05:296:20:10:33
Block: 44479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360136 RingCT/type: yes/0
Extra: 01474f6a6794d663b51fd1a6a873b151d8cda3544842e1204bbb765cce367bd6ce02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 437.142921052000 dcy

stealth address amount amount idx
00: 19e3d7282b508994616d55a5fe3b81dca7b8a23528931bdf12d25f2e1cf9a797 437.142921052000 80963 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": 44489, "vin": [ { "gen": { "height": 44479 } } ], "vout": [ { "amount": 437142921052, "target": { "key": "19e3d7282b508994616d55a5fe3b81dca7b8a23528931bdf12d25f2e1cf9a797" } } ], "extra": [ 1, 71, 79, 106, 103, 148, 214, 99, 181, 31, 209, 166, 168, 115, 177, 81, 216, 205, 163, 84, 72, 66, 225, 32, 75, 187, 118, 92, 206, 54, 123, 214, 206, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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