Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1adf49ed3471aeb66d4496ef99d602b59c8d9b5925125e042b6b1717216635

Tx prefix hash: 484f10a4c20d5b5bcadc2af7dc1bd65b700070b733d5ed57d7c00f921aa5b900
Tx public key: d214ca3f7a0e401bbd743429dcf3e38b7924936c29e6e1b50d431234af013f2f
Timestamp: 1577646823 Timestamp [UCT]: 2019-12-29 19:13:43 Age [y:d:h:m:s]: 05:035:06:31:47
Block: 34504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174956 RingCT/type: yes/0
Extra: 01d214ca3f7a0e401bbd743429dcf3e38b7924936c29e6e1b50d431234af013f2f0211000000034ac5aa02000000000000000000

1 output(s) for total of 471.709671156000 dcy

stealth address amount amount idx
00: 5534f5c96c6b9fbd444b3cd08c411a2cb1afb7db8789b14e072f2b4adaa0c00a 471.709671156000 58080 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": 34514, "vin": [ { "gen": { "height": 34504 } } ], "vout": [ { "amount": 471709671156, "target": { "key": "5534f5c96c6b9fbd444b3cd08c411a2cb1afb7db8789b14e072f2b4adaa0c00a" } } ], "extra": [ 1, 210, 20, 202, 63, 122, 14, 64, 27, 189, 116, 52, 41, 220, 243, 227, 139, 121, 36, 147, 108, 41, 230, 225, 181, 13, 67, 18, 52, 175, 1, 63, 47, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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