Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9799407c240e7c41350e615de9268d650c60e17dea8db09e5393adc4c205c5c6

Tx prefix hash: 7b4d8ee67864341fb1a3f1eda24964591f754be2f50304b22fb3c6fe2a2e46f3
Tx public key: 270418292b5a0d36325ef96b541a35f8ee72fb2edcffc7b70107d0762b3ddfb1
Timestamp: 1707509829 Timestamp [UCT]: 2024-02-09 20:17:09 Age [y:d:h:m:s]: 01:317:05:44:08
Block: 953998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485557 RingCT/type: yes/0
Extra: 01270418292b5a0d36325ef96b541a35f8ee72fb2edcffc7b70107d0762b3ddfb10211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f5c364e4cced8784888b22e424474f03c0cc40ab3ebed659dbf3b5293401c8 0.600000000000 1413270 of 15

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": 954008, "vin": [ { "gen": { "height": 953998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f5c364e4cced8784888b22e424474f03c0cc40ab3ebed659dbf3b5293401c8" } } ], "extra": [ 1, 39, 4, 24, 41, 43, 90, 13, 54, 50, 94, 249, 107, 84, 26, 53, 248, 238, 114, 251, 46, 220, 255, 199, 183, 1, 7, 208, 118, 43, 61, 223, 177, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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