Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44f25a23fcbc1380c2793e7ee082e9f6c79ff5c97549012a5a2f75fbe81260c

Tx prefix hash: cebd4e920cd93fff17f8c708449461a4801ed8a427b027fc0d6b1c58ad4c5b4f
Tx public key: da08239e086c246e650eb40321bb6aa0b779ecbdb016704c48298a9be5cb88ad
Timestamp: 1735706066 Timestamp [UCT]: 2025-01-01 04:34:26 Age [y:d:h:m:s]: 01:004:15:32:05
Block: 1187630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261789 RingCT/type: yes/0
Extra: 01da08239e086c246e650eb40321bb6aa0b779ecbdb016704c48298a9be5cb88ad021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d7bb582d6949c17980c43d0c00e23975a1ba8d3b79849bce90df24366ada296 0.600000000000 1674123 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": 1187640, "vin": [ { "gen": { "height": 1187630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d7bb582d6949c17980c43d0c00e23975a1ba8d3b79849bce90df24366ada296" } } ], "extra": [ 1, 218, 8, 35, 158, 8, 108, 36, 110, 101, 14, 180, 3, 33, 187, 106, 160, 183, 121, 236, 189, 176, 22, 112, 76, 72, 41, 138, 155, 229, 203, 136, 173, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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