Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3d6ba10bb5dc64afb1b86b84fafaafc6bbe17d6d36756ed3c9bad800e6c58e

Tx prefix hash: 6094818ccd6f0437582fcada6f3fbab0d639fe59876b1d72a81454ee552a5f0b
Tx public key: 6994003aaff197e7424315fd1aeca77d00ff2a5d0e79e4d356a1d5898605a5b5
Timestamp: 1677427954 Timestamp [UCT]: 2023-02-26 16:12:34 Age [y:d:h:m:s]: 01:319:03:35:48
Block: 705488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489040 RingCT/type: yes/0
Extra: 016994003aaff197e7424315fd1aeca77d00ff2a5d0e79e4d356a1d5898605a5b502110000000483600029000000000000000000

1 output(s) for total of 2.821144291000 dcy

stealth address amount amount idx
00: 150e4b95f26540abc27e2c537902d9e5cee28c193e573b93bbb8ee43fc7f731a 2.821144291000 1149191 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": 705498, "vin": [ { "gen": { "height": 705488 } } ], "vout": [ { "amount": 2821144291, "target": { "key": "150e4b95f26540abc27e2c537902d9e5cee28c193e573b93bbb8ee43fc7f731a" } } ], "extra": [ 1, 105, 148, 0, 58, 175, 241, 151, 231, 66, 67, 21, 253, 26, 236, 167, 125, 0, 255, 42, 93, 14, 121, 228, 211, 86, 161, 213, 137, 134, 5, 165, 181, 2, 17, 0, 0, 0, 4, 131, 96, 0, 41, 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