Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfca3495c204dd5f3843b23ba396547b44006a63cb79ca1a8ecf5178ab911da3

Tx prefix hash: f17b5e034af0d937a60c62dca04e4ee99c0117700a808ef40aeb31a28428d100
Tx public key: a3e36c937195c063ea7bfb0c9e3fa4287cb14c23749a4fabefa694f06bc060ae
Timestamp: 1715596388 Timestamp [UCT]: 2024-05-13 10:33:08 Age [y:d:h:m:s]: 00:340:04:20:09
Block: 1021070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243145 RingCT/type: yes/0
Extra: 01a3e36c937195c063ea7bfb0c9e3fa4287cb14c23749a4fabefa694f06bc060ae02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c20b724d4ff602b8914c9b33324c74950eb4b2e48ecb2266f9a6ca9c60a1ab 0.600000000000 1485257 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": 1021080, "vin": [ { "gen": { "height": 1021070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c20b724d4ff602b8914c9b33324c74950eb4b2e48ecb2266f9a6ca9c60a1ab" } } ], "extra": [ 1, 163, 227, 108, 147, 113, 149, 192, 99, 234, 123, 251, 12, 158, 63, 164, 40, 124, 177, 76, 35, 116, 154, 79, 171, 239, 166, 148, 240, 107, 192, 96, 174, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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