Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25db60a4abcb0cfa263377b2aec510df2ddf7253c9c008af471fb350d3f2c71f

Tx prefix hash: 78d9288b16a04d03ff9db692ae7ad79dd956f72238928c67e899afb4db184478
Tx public key: c176445b8c91aa6c165aa7cd96f4db4de802cd5ebf70553672422b29574ab704
Timestamp: 1581080203 Timestamp [UCT]: 2020-02-07 12:56:43 Age [y:d:h:m:s]: 05:000:07:07:02
Block: 60119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152736 RingCT/type: yes/0
Extra: 01c176445b8c91aa6c165aa7cd96f4db4de802cd5ebf70553672422b29574ab7040211000000044ac5aa02000000000000000000

1 output(s) for total of 387.973099655000 dcy

stealth address amount amount idx
00: 394b4996b315929cdcba2e3d1998ce3e10f11a963fcdd083165d76d9ddff3fb4 387.973099655000 110929 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": 60129, "vin": [ { "gen": { "height": 60119 } } ], "vout": [ { "amount": 387973099655, "target": { "key": "394b4996b315929cdcba2e3d1998ce3e10f11a963fcdd083165d76d9ddff3fb4" } } ], "extra": [ 1, 193, 118, 68, 91, 140, 145, 170, 108, 22, 90, 167, 205, 150, 244, 219, 77, 232, 2, 205, 94, 191, 112, 85, 54, 114, 66, 43, 41, 87, 74, 183, 4, 2, 17, 0, 0, 0, 4, 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