Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273a917b0e57fe4c64fa4f0a4577ae9d7cc97b312a19a7f23ddd483f54f4d7dc

Tx prefix hash: 183e60c33d7104f2e623fd1a50eff336c0a69a97b6fe61e55f8441f664dbc71f
Tx public key: 7ec92b4721222936654795ed117eeb740ef84c81e6f4acead61aaf59b6653338
Timestamp: 1582922223 Timestamp [UCT]: 2020-02-28 20:37:03 Age [y:d:h:m:s]: 04:251:08:20:15
Block: 73606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073252 RingCT/type: yes/0
Extra: 017ec92b4721222936654795ed117eeb740ef84c81e6f4acead61aaf59b66533380211000000188a2ee0d9000000000000000000

1 output(s) for total of 350.062528047000 dcy

stealth address amount amount idx
00: fecdcd791b5f33c1c28447086d40a5ae805d53a09e6556c1c9cbe2098e14524b 350.062528047000 135822 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": 73616, "vin": [ { "gen": { "height": 73606 } } ], "vout": [ { "amount": 350062528047, "target": { "key": "fecdcd791b5f33c1c28447086d40a5ae805d53a09e6556c1c9cbe2098e14524b" } } ], "extra": [ 1, 126, 201, 43, 71, 33, 34, 41, 54, 101, 71, 149, 237, 17, 126, 235, 116, 14, 248, 76, 129, 230, 244, 172, 234, 214, 26, 175, 89, 182, 101, 51, 56, 2, 17, 0, 0, 0, 24, 138, 46, 224, 217, 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