Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf5ee4dccf61770fbfc0783bda76ec0e0f13893814db6f2a778dd8be8c18afe

Tx prefix hash: 86c9c111d4bde6f12cd9ea7f1ab21f85e3c7823e2aaaac2e61580d7b85666957
Tx public key: f4140c043084a522dbab3f93c84663366c2554483a88f80df18dcef5830c7003
Timestamp: 1701235716 Timestamp [UCT]: 2023-11-29 05:28:36 Age [y:d:h:m:s]: 01:345:11:26:49
Block: 901987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505791 RingCT/type: yes/0
Extra: 01f4140c043084a522dbab3f93c84663366c2554483a88f80df18dcef5830c700302110000000833af99f4000000000000000000

1 output(s) for total of 0.630002999000 dcy

stealth address amount amount idx
00: 39ac97b5626cf987170fe699b0b77dbb3702ae7c2d73bd189257ce5db2447316 0.630002999000 1358588 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": 901997, "vin": [ { "gen": { "height": 901987 } } ], "vout": [ { "amount": 630002999, "target": { "key": "39ac97b5626cf987170fe699b0b77dbb3702ae7c2d73bd189257ce5db2447316" } } ], "extra": [ 1, 244, 20, 12, 4, 48, 132, 165, 34, 219, 171, 63, 147, 200, 70, 99, 54, 108, 37, 84, 72, 58, 136, 248, 13, 241, 141, 206, 245, 131, 12, 112, 3, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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