Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3015c264ad44d3aef3bfd7a0e4a795dcbe5d08ee975586d9fe1697dc3f842fe5

Tx prefix hash: 58acd962000d57cdd60101fc35cb548ae77c25d371d692945b1c113484973933
Tx public key: 6d7d7f325db90e6a2d55bb1057b28f3e7ebe9b2e8474d0bcc59c320822794cb5
Timestamp: 1717140128 Timestamp [UCT]: 2024-05-31 07:22:08 Age [y:d:h:m:s]: 00:304:17:39:31
Block: 1033852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217780 RingCT/type: yes/0
Extra: 016d7d7f325db90e6a2d55bb1057b28f3e7ebe9b2e8474d0bcc59c320822794cb502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b86920ee18510d0752f417afe489d38476cc18048cb964b0f58f06f0560354 0.600000000000 1502325 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": 1033862, "vin": [ { "gen": { "height": 1033852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b86920ee18510d0752f417afe489d38476cc18048cb964b0f58f06f0560354" } } ], "extra": [ 1, 109, 125, 127, 50, 93, 185, 14, 106, 45, 85, 187, 16, 87, 178, 143, 62, 126, 190, 155, 46, 132, 116, 208, 188, 197, 156, 50, 8, 34, 121, 76, 181, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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