Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a173e21f262f2bbbbee727e543cc7b248cc5b7a67f37491445001d117a40a2aa

Tx prefix hash: 0de421e6da5eb8a039dea9094a3c35d2d3031d0b5e667916a3ab6fb35cc8250b
Tx public key: 6d6a018ee8b21a80e06492006e5665fe8f8e7152bcc9a9850fe12d813e5d6e0d
Timestamp: 1635757117 Timestamp [UCT]: 2021-11-01 08:58:37 Age [y:d:h:m:s]: 04:004:05:40:31
Block: 364931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1039923 RingCT/type: yes/0
Extra: 016d6a018ee8b21a80e06492006e5665fe8f8e7152bcc9a9850fe12d813e5d6e0d021100000001745f00f8000000000000000000

1 output(s) for total of 37.916872539000 dcy

stealth address amount amount idx
00: 2ec0106dcbbc6e98389d523ef2e0c84f5114ba1cb14dda0798519217da79b9ec 37.916872539000 741177 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": 364941, "vin": [ { "gen": { "height": 364931 } } ], "vout": [ { "amount": 37916872539, "target": { "key": "2ec0106dcbbc6e98389d523ef2e0c84f5114ba1cb14dda0798519217da79b9ec" } } ], "extra": [ 1, 109, 106, 1, 142, 232, 178, 26, 128, 224, 100, 146, 0, 110, 86, 101, 254, 143, 142, 113, 82, 188, 201, 169, 133, 15, 225, 45, 129, 62, 93, 110, 13, 2, 17, 0, 0, 0, 1, 116, 95, 0, 248, 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