Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b814cacf9fb3ecc19447a24334f84a649475f4cc17f024ec37b241a0242508f

Tx prefix hash: 960ea7be07ebe803d93c430ab0f559a07e71096992829acf5821e5ca4672e2db
Tx public key: 1b006a1754a7357fb4f828770f631208bf3a85e1536370e56a39d6e4ac4594f4
Timestamp: 1574511925 Timestamp [UCT]: 2019-11-23 12:25:25 Age [y:d:h:m:s]: 05:103:01:01:37
Block: 15521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1216465 RingCT/type: yes/0
Extra: 011b006a1754a7357fb4f828770f631208bf3a85e1536370e56a39d6e4ac4594f4021100000007354bbe3b000000000000000000

1 output(s) for total of 545.221994711000 dcy

stealth address amount amount idx
00: cd4acdee8636ef40ae08c094b129f41e767b235d862b97f0d0830b02824f673c 545.221994711000 20852 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": 15531, "vin": [ { "gen": { "height": 15521 } } ], "vout": [ { "amount": 545221994711, "target": { "key": "cd4acdee8636ef40ae08c094b129f41e767b235d862b97f0d0830b02824f673c" } } ], "extra": [ 1, 27, 0, 106, 23, 84, 167, 53, 127, 180, 248, 40, 119, 15, 99, 18, 8, 191, 58, 133, 225, 83, 99, 112, 229, 106, 57, 214, 228, 172, 69, 148, 244, 2, 17, 0, 0, 0, 7, 53, 75, 190, 59, 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