Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b581055e73cc59eb2a7e4a28d0e5a8673407bd99443dab8d3979ee4cf2dd98ca

Tx prefix hash: 2b14a29ab27cfe6cfee8ae328e4f6149d20cb6ed344be4208473adaea398346e
Tx public key: 2e1f08668ae9ea362ce79e420aeb07e717a19e4209e20b45785c993c64b7cd2d
Timestamp: 1706847903 Timestamp [UCT]: 2024-02-02 04:25:03 Age [y:d:h:m:s]: 01:028:16:04:22
Block: 948507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281524 RingCT/type: yes/0
Extra: 012e1f08668ae9ea362ce79e420aeb07e717a19e4209e20b45785c993c64b7cd2d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be27df5cb8de6ae60e06ec558e8c8da6449cafa564a66208d733c678ee812028 0.600000000000 1406927 of 15

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": 948517, "vin": [ { "gen": { "height": 948507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be27df5cb8de6ae60e06ec558e8c8da6449cafa564a66208d733c678ee812028" } } ], "extra": [ 1, 46, 31, 8, 102, 138, 233, 234, 54, 44, 231, 158, 66, 10, 235, 7, 231, 23, 161, 158, 66, 9, 226, 11, 69, 120, 92, 153, 60, 100, 183, 205, 45, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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