Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779b560627316fe00c2bf1a0f5d6423a419d3456829bbdb0b95c7a45eac1893d

Tx prefix hash: 128736a3ea004797fadd1eddf7e6965a711d04d66879dd8683cce0c6414d40f7
Tx public key: 9a54d570b19340361390125de8df492a8cef82e99cbea34df0d19e919e99b41e
Timestamp: 1706515135 Timestamp [UCT]: 2024-01-29 07:58:55 Age [y:d:h:m:s]: 01:079:16:51:12
Block: 945734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318045 RingCT/type: yes/0
Extra: 019a54d570b19340361390125de8df492a8cef82e99cbea34df0d19e919e99b41e02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c90f3dc58ddce903ab97199dfd3c223f70b5e4bf4e58e978d7916e6cea08755 0.600000000000 1404052 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": 945744, "vin": [ { "gen": { "height": 945734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c90f3dc58ddce903ab97199dfd3c223f70b5e4bf4e58e978d7916e6cea08755" } } ], "extra": [ 1, 154, 84, 213, 112, 177, 147, 64, 54, 19, 144, 18, 93, 232, 223, 73, 42, 140, 239, 130, 233, 156, 190, 163, 77, 240, 209, 158, 145, 158, 153, 180, 30, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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