Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b44fb4875de48a91e15fadd00b99722000350ed6f202e89e20627dcdd023c871

Tx prefix hash: 62efa73ffcdf0f81ec3479665e4ba07c94715fed0c4713cf11bb59c85e550f5a
Tx public key: f2ce6566c45f8afad91a4379d559d5644bf9b2c8c8effcb89ed9da011b79e98d
Timestamp: 1638151111 Timestamp [UCT]: 2021-11-29 01:58:31 Age [y:d:h:m:s]: 03:031:06:10:20
Block: 384351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801239 RingCT/type: yes/0
Extra: 01f2ce6566c45f8afad91a4379d559d5644bf9b2c8c8effcb89ed9da011b79e98d0211000000111cab2639000000000000000000

1 output(s) for total of 32.695917656000 dcy

stealth address amount amount idx
00: c2ec37b345dc962c7c72f43548c3159d2c7c7fcb8e6b9ea9e25c8a624193238f 32.695917656000 775790 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": 384361, "vin": [ { "gen": { "height": 384351 } } ], "vout": [ { "amount": 32695917656, "target": { "key": "c2ec37b345dc962c7c72f43548c3159d2c7c7fcb8e6b9ea9e25c8a624193238f" } } ], "extra": [ 1, 242, 206, 101, 102, 196, 95, 138, 250, 217, 26, 67, 121, 213, 89, 213, 100, 75, 249, 178, 200, 200, 239, 252, 184, 158, 217, 218, 1, 27, 121, 233, 141, 2, 17, 0, 0, 0, 17, 28, 171, 38, 57, 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