Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 178d7283a5c12796b78c216205992ca77d6263e6d40fdf1975a2556eaee2ae19

Tx prefix hash: 70bc04e2b7fed82c318984de0ea4f2acb2c60c9713f270aebe86d77a261177e0
Tx public key: 5f49f4b255a7433558c4b8483ef7bd8372a1a661561cd9ff50a23ad0795fb84e
Timestamp: 1577812571 Timestamp [UCT]: 2019-12-31 17:16:11 Age [y:d:h:m:s]: 04:121:08:30:44
Block: 35905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 975563 RingCT/type: yes/0
Extra: 015f49f4b255a7433558c4b8483ef7bd8372a1a661561cd9ff50a23ad0795fb84e0211000000404943cd9f000000000000000000

1 output(s) for total of 466.694501084000 dcy

stealth address amount amount idx
00: deeb26504f0673bb9a9cf80bf98dcc895ce8fe7f5b1823e9370d8396842e4ee2 466.694501084000 60640 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": 35915, "vin": [ { "gen": { "height": 35905 } } ], "vout": [ { "amount": 466694501084, "target": { "key": "deeb26504f0673bb9a9cf80bf98dcc895ce8fe7f5b1823e9370d8396842e4ee2" } } ], "extra": [ 1, 95, 73, 244, 178, 85, 167, 67, 53, 88, 196, 184, 72, 62, 247, 189, 131, 114, 161, 166, 97, 86, 28, 217, 255, 80, 162, 58, 208, 121, 95, 184, 78, 2, 17, 0, 0, 0, 64, 73, 67, 205, 159, 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