Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e440ebcd758abcb41335a9045dd70e5406cc3ec69cc497dbe5fcce3426cfcf

Tx prefix hash: 52e859808e1e37624b232dfecbd1c28f99435bddddee5069bb5f590081082971
Tx public key: 6df7bb75f3a5edda3fb1b5f086200dd349445b3de8e9b0bc82d111789ee8ed68
Timestamp: 1608481304 Timestamp [UCT]: 2020-12-20 16:21:44 Age [y:d:h:m:s]: 04:076:16:29:11
Block: 165894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067383 RingCT/type: yes/0
Extra: 016df7bb75f3a5edda3fb1b5f086200dd349445b3de8e9b0bc82d111789ee8ed680211000038bab9b01d0b000000000000000000

1 output(s) for total of 173.111127067000 dcy

stealth address amount amount idx
00: e2d015c4bf94541c7f01f0d1112ffa2992a7812b4238e452f90e839d340acb74 173.111127067000 302681 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": 165904, "vin": [ { "gen": { "height": 165894 } } ], "vout": [ { "amount": 173111127067, "target": { "key": "e2d015c4bf94541c7f01f0d1112ffa2992a7812b4238e452f90e839d340acb74" } } ], "extra": [ 1, 109, 247, 187, 117, 243, 165, 237, 218, 63, 177, 181, 240, 134, 32, 13, 211, 73, 68, 91, 61, 232, 233, 176, 188, 130, 209, 17, 120, 158, 232, 237, 104, 2, 17, 0, 0, 56, 186, 185, 176, 29, 11, 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