Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9ea42e2b38c6fb36235aaddd97aeae9aa823e0674268135a8b034108d2417f

Tx prefix hash: d9e76b8ad90bf825447c4a9490f5098c07f156d8d61d485b279253d5e6fd09a0
Tx public key: 41edf66d1d93f861c377070678685aee1e1d39d76c55c4e33d8c257e6742560b
Timestamp: 1737156919 Timestamp [UCT]: 2025-01-17 23:35:19 Age [y:d:h:m:s]: 00:058:11:41:40
Block: 1199645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41594 RingCT/type: yes/0
Extra: 0141edf66d1d93f861c377070678685aee1e1d39d76c55c4e33d8c257e6742560b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52c970971942bc31d5d07e368fdb620bcb6ce1f557380c70fb1e65ff36a4b39c 0.600000000000 1686278 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": 1199655, "vin": [ { "gen": { "height": 1199645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c970971942bc31d5d07e368fdb620bcb6ce1f557380c70fb1e65ff36a4b39c" } } ], "extra": [ 1, 65, 237, 246, 109, 29, 147, 248, 97, 195, 119, 7, 6, 120, 104, 90, 238, 30, 29, 57, 215, 108, 85, 196, 227, 61, 140, 37, 126, 103, 66, 86, 11, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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