Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcbfd3ebd86179cb3db8d4c9778274e0257697ddf5d6d7032a654e2d17965ff6

Tx prefix hash: 8b8ca1a79edc920166a0f03dc67bfaae80f9c6865d7b111d644bbea437547a1b
Tx public key: c6bf509839553593e615511cb150daac8392a3690f9a4c7d48d850a2e1dfae23
Timestamp: 1735770102 Timestamp [UCT]: 2025-01-01 22:21:42 Age [y:d:h:m:s]: 00:167:00:34:32
Block: 1188163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119083 RingCT/type: yes/0
Extra: 01c6bf509839553593e615511cb150daac8392a3690f9a4c7d48d850a2e1dfae23021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc8a47e6093b4137b36cefba34897906546a32f31fdb0f5d6a4e7b39161c4471 0.600000000000 1674664 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": 1188173, "vin": [ { "gen": { "height": 1188163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc8a47e6093b4137b36cefba34897906546a32f31fdb0f5d6a4e7b39161c4471" } } ], "extra": [ 1, 198, 191, 80, 152, 57, 85, 53, 147, 230, 21, 81, 28, 177, 80, 218, 172, 131, 146, 163, 105, 15, 154, 76, 125, 72, 216, 80, 162, 225, 223, 174, 35, 2, 17, 0, 0, 0, 7, 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