Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc72957fa35fb0a1ed5046e19cea593f8e52cc40f272a29b5e17d0f0ce0f60c6

Tx prefix hash: 1e4a315f54ecf228eb807014ecd8d928827909c3ae9b268116d41d31724572d2
Tx public key: 3e88d0980c8083bcb175efddd84e36dd606669a436bd2b8f0ab44abc63ebb170
Timestamp: 1673830542 Timestamp [UCT]: 2023-01-16 00:55:42 Age [y:d:h:m:s]: 02:080:09:34:54
Block: 675644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579139 RingCT/type: yes/0
Extra: 013e88d0980c8083bcb175efddd84e36dd606669a436bd2b8f0ab44abc63ebb170021100000001faf35c9c000000000000000000

1 output(s) for total of 3.542508523000 dcy

stealth address amount amount idx
00: d8b749e07e17b49627cb9ff12a8c0587c03b00b6afa35c63c6fa878c6def9ca8 3.542508523000 1117327 of 0

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": 675654, "vin": [ { "gen": { "height": 675644 } } ], "vout": [ { "amount": 3542508523, "target": { "key": "d8b749e07e17b49627cb9ff12a8c0587c03b00b6afa35c63c6fa878c6def9ca8" } } ], "extra": [ 1, 62, 136, 208, 152, 12, 128, 131, 188, 177, 117, 239, 221, 216, 78, 54, 221, 96, 102, 105, 164, 54, 189, 43, 143, 10, 180, 74, 188, 99, 235, 177, 112, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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