Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46963485836a2a954163e8bff236df3884c0f5a163643a061a972787fb8b0246

Tx prefix hash: 505a048f01b647145c0aa7391fe7092f1565ef5410c9bdded6322119ea204e3f
Tx public key: d0e1daf88ad0a4118f969563c009c606b3902864aea6ab0f4752ecc193695fae
Timestamp: 1634824015 Timestamp [UCT]: 2021-10-21 13:46:55 Age [y:d:h:m:s]: 03:068:12:25:31
Block: 357484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827218 RingCT/type: yes/0
Extra: 01d0e1daf88ad0a4118f969563c009c606b3902864aea6ab0f4752ecc193695fae0211000000105410958b000000000000000000

1 output(s) for total of 40.133544931000 dcy

stealth address amount amount idx
00: 331ceafb25907c74d089e16b1ce60d2e2c9d58dd38d49d83a9a1086b62a842c8 40.133544931000 728928 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": 357494, "vin": [ { "gen": { "height": 357484 } } ], "vout": [ { "amount": 40133544931, "target": { "key": "331ceafb25907c74d089e16b1ce60d2e2c9d58dd38d49d83a9a1086b62a842c8" } } ], "extra": [ 1, 208, 225, 218, 248, 138, 208, 164, 17, 143, 150, 149, 99, 192, 9, 198, 6, 179, 144, 40, 100, 174, 166, 171, 15, 71, 82, 236, 193, 147, 105, 95, 174, 2, 17, 0, 0, 0, 16, 84, 16, 149, 139, 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