Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec9c2502e45d8782709175b4da39cfd25f3791689789b155e7c682b691233a8e

Tx prefix hash: 3c829a22ca21b0a9fcdaa6cef9d42538c5408d66335a3122d963c01c8b796b62
Tx public key: c3f763422be5da32a898dc4aa69789a0e30d740acc7bf4e6c37c534ee23f6e0d
Timestamp: 1705466209 Timestamp [UCT]: 2024-01-17 04:36:49 Age [y:d:h:m:s]: 01:303:23:54:16
Block: 937033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476106 RingCT/type: yes/0
Extra: 01c3f763422be5da32a898dc4aa69789a0e30d740acc7bf4e6c37c534ee23f6e0d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ead9591e15c100e7c616dbd9bb51767d3b5c19d2f9cbf37a152a8f1209cc9c 0.600000000000 1395077 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": 937043, "vin": [ { "gen": { "height": 937033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ead9591e15c100e7c616dbd9bb51767d3b5c19d2f9cbf37a152a8f1209cc9c" } } ], "extra": [ 1, 195, 247, 99, 66, 43, 229, 218, 50, 168, 152, 220, 74, 166, 151, 137, 160, 227, 13, 116, 10, 204, 123, 244, 230, 195, 124, 83, 78, 226, 63, 110, 13, 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