Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1e176fee6b1efc57ef58cfdbe93593f3181b67f707de14ce2d0eb6ee2cfd4f

Tx prefix hash: d40633be1cdec6602c637670a528843eb55ff33b875cd0572ac8fc806bb41774
Tx public key: 6fd0fb910a17e994d4e1d4ce2c69a7033029bdf413db1e75548b9fce3cac9925
Timestamp: 1718495191 Timestamp [UCT]: 2024-06-15 23:46:31 Age [y:d:h:m:s]: 00:221:13:27:48
Block: 1045101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158487 RingCT/type: yes/0
Extra: 016fd0fb910a17e994d4e1d4ce2c69a7033029bdf413db1e75548b9fce3cac99250211000000018fda9b2d000000000000000000

1 output(s) for total of 0.613580000000 dcy

stealth address amount amount idx
00: 21d8baea3911b9cf095198b227781014588ecf37ff59190bac5c8fad40c99850 0.613580000000 1514582 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": 1045111, "vin": [ { "gen": { "height": 1045101 } } ], "vout": [ { "amount": 613580000, "target": { "key": "21d8baea3911b9cf095198b227781014588ecf37ff59190bac5c8fad40c99850" } } ], "extra": [ 1, 111, 208, 251, 145, 10, 23, 233, 148, 212, 225, 212, 206, 44, 105, 167, 3, 48, 41, 189, 244, 19, 219, 30, 117, 84, 139, 159, 206, 60, 172, 153, 37, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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