Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbaace198f96176331bc5408ecae7c147d9507576e2ec05f65ce0f0f1ddfc8db

Tx prefix hash: 890fdf499ddbd4e7711e6c39976ea5c5064940b9c21db49553c9efe9e9b388b7
Tx public key: a120545814b74a3b1fd285b841deefef0eef3750851cf79aeaccc55be031623e
Timestamp: 1577059094 Timestamp [UCT]: 2019-12-22 23:58:14 Age [y:d:h:m:s]: 05:314:07:00:38
Block: 29775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371991 RingCT/type: yes/0
Extra: 01a120545814b74a3b1fd285b841deefef0eef3750851cf79aeaccc55be031623e02110000002dd81c26c0000000000000000000

1 output(s) for total of 489.039487242000 dcy

stealth address amount amount idx
00: c72f64a3dd15e691c9a2e7544e35188d779209ac7f5e19de1796717476ab9eea 489.039487242000 49067 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": 29785, "vin": [ { "gen": { "height": 29775 } } ], "vout": [ { "amount": 489039487242, "target": { "key": "c72f64a3dd15e691c9a2e7544e35188d779209ac7f5e19de1796717476ab9eea" } } ], "extra": [ 1, 161, 32, 84, 88, 20, 183, 74, 59, 31, 210, 133, 184, 65, 222, 239, 239, 14, 239, 55, 80, 133, 28, 247, 154, 234, 204, 197, 91, 224, 49, 98, 62, 2, 17, 0, 0, 0, 45, 216, 28, 38, 192, 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