Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1c5e4761516197d0cb7375d4e6963fbef5acdecf3497683e66da89776ce141

Tx prefix hash: d329601899c6bc34166ca0399ae9afbb4276cff762c5e45a1c523e01a47ddd9b
Tx public key: 7a4a0cef54232ecbe302a4bdb9905814fa9f3380e3857c8c6808913444a57c01
Timestamp: 1715116282 Timestamp [UCT]: 2024-05-07 21:11:22 Age [y:d:h:m:s]: 00:325:10:02:14
Block: 1017070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232601 RingCT/type: yes/0
Extra: 017a4a0cef54232ecbe302a4bdb9905814fa9f3380e3857c8c6808913444a57c0102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59cb1a6674a9fe1c7b0560a80ef3c0f736c409e2c605776c501d7e0c795a9d5f 0.600000000000 1480837 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": 1017080, "vin": [ { "gen": { "height": 1017070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59cb1a6674a9fe1c7b0560a80ef3c0f736c409e2c605776c501d7e0c795a9d5f" } } ], "extra": [ 1, 122, 74, 12, 239, 84, 35, 46, 203, 227, 2, 164, 189, 185, 144, 88, 20, 250, 159, 51, 128, 227, 133, 124, 140, 104, 8, 145, 52, 68, 165, 124, 1, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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