Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5950997860dda37698ea57c3e9c45fe116aeb2d55c6571a0c4bedaaa10fa00b2

Tx prefix hash: f0c4ae6f0aa76fb5a985f79ecc4ce65dcf2455ef28d1004e93d6a0411ca83464
Tx public key: f4a4e6797fc8c23766a5094ef34f3eedcf831b0aa7fb0c68400eb14f07da2677
Timestamp: 1708267633 Timestamp [UCT]: 2024-02-18 14:47:13 Age [y:d:h:m:s]: 00:280:13:10:27
Block: 960290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200850 RingCT/type: yes/0
Extra: 01f4a4e6797fc8c23766a5094ef34f3eedcf831b0aa7fb0c68400eb14f07da26770211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5b17a1c829014ae09d34f10d379ee0f2b4f8c715dd970a954b167a70ff172e 0.600000000000 1419853 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": 960300, "vin": [ { "gen": { "height": 960290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5b17a1c829014ae09d34f10d379ee0f2b4f8c715dd970a954b167a70ff172e" } } ], "extra": [ 1, 244, 164, 230, 121, 127, 200, 194, 55, 102, 165, 9, 78, 243, 79, 62, 237, 207, 131, 27, 10, 167, 251, 12, 104, 64, 14, 177, 79, 7, 218, 38, 119, 2, 17, 0, 0, 0, 8, 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