Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbcf5b73c1a1c922be9db44e116107d99e4938a1acf2cab18cf27380f8a598bb

Tx prefix hash: b36d08b427ff39d2d591a63f1475b6f78d69c87a49cabf7858f8349ab8c62291
Tx public key: 509930e9312a86cab3e23d1738503b0f2c69dff5c9483199abcb7bbb855e54ef
Timestamp: 1759812181 Timestamp [UCT]: 2025-10-07 04:43:01 Age [y:d:h:m:s]: 00:035:19:55:22
Block: 1384492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25672 RingCT/type: yes/0
Extra: 01509930e9312a86cab3e23d1738503b0f2c69dff5c9483199abcb7bbb855e54ef02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f945e57f4f23794be9787af29aea4e6e5f69c822f8f005fd9d1e5fa3b0971629 0.600000000000 1872645 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": 1384502, "vin": [ { "gen": { "height": 1384492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f945e57f4f23794be9787af29aea4e6e5f69c822f8f005fd9d1e5fa3b0971629" } } ], "extra": [ 1, 80, 153, 48, 233, 49, 42, 134, 202, 179, 226, 61, 23, 56, 80, 59, 15, 44, 105, 223, 245, 201, 72, 49, 153, 171, 203, 123, 187, 133, 94, 84, 239, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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