Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f1823c418cd428b183a841224562ca5f513046890cc8643aa2292e0d9fd99eb

Tx prefix hash: 6d916ad84b2d550bc2d70b4fb097e2bb60ae3e2ee2410ad76cd8c3f492d3edd8
Tx public key: 087e92867ad0caaf8317c7028b83e3b285eae0b39449f3d4e8b3f41ea4e8db7b
Timestamp: 1610259472 Timestamp [UCT]: 2021-01-10 06:17:52 Age [y:d:h:m:s]: 05:024:09:27:19
Block: 176938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1292210 RingCT/type: yes/0
Extra: 01087e92867ad0caaf8317c7028b83e3b285eae0b39449f3d4e8b3f41ea4e8db7b021100000046508974f9000000000000000000

1 output(s) for total of 159.130756493000 dcy

stealth address amount amount idx
00: b652dda31c2e11f3784e1994ac39142bdaee733d754c5994b0fa6b0977aa418b 159.130756493000 339434 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": 176948, "vin": [ { "gen": { "height": 176938 } } ], "vout": [ { "amount": 159130756493, "target": { "key": "b652dda31c2e11f3784e1994ac39142bdaee733d754c5994b0fa6b0977aa418b" } } ], "extra": [ 1, 8, 126, 146, 134, 122, 208, 202, 175, 131, 23, 199, 2, 139, 131, 227, 178, 133, 234, 224, 179, 148, 73, 243, 212, 232, 179, 244, 30, 164, 232, 219, 123, 2, 17, 0, 0, 0, 70, 80, 137, 116, 249, 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