Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4d7f8ecc75e9813f0321ce9cfc1af16ea01ba42f78ae7bca1aace101d2d58b

Tx prefix hash: 27bec061e34adf3651238d6bd9c3228630d7525258902954bccf6b8522dc13c8
Tx public key: a3bd917f2d79cc1bce277002d5201bcc8313061082daa1bb5082af0fa73b4d6d
Timestamp: 1717893477 Timestamp [UCT]: 2024-06-09 00:37:57 Age [y:d:h:m:s]: 00:235:17:37:58
Block: 1040088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168439 RingCT/type: yes/0
Extra: 01a3bd917f2d79cc1bce277002d5201bcc8313061082daa1bb5082af0fa73b4d6d021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdefc78937abe13001f5a3681ce1a240dddfe5e3a6d93ec0ae1d6bc05af23cdd 0.600000000000 1508743 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": 1040098, "vin": [ { "gen": { "height": 1040088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdefc78937abe13001f5a3681ce1a240dddfe5e3a6d93ec0ae1d6bc05af23cdd" } } ], "extra": [ 1, 163, 189, 145, 127, 45, 121, 204, 27, 206, 39, 112, 2, 213, 32, 27, 204, 131, 19, 6, 16, 130, 218, 161, 187, 80, 130, 175, 15, 167, 59, 77, 109, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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