Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b863a202df79ebae719d887c930a49580726b3bcdcb0a42e261b2ae55b0b506

Tx prefix hash: 2e5bd30206049d55e32d9a3c8426e7aa0345e7af94b1c7c411b95e984544bc86
Tx public key: fa02cb78f582ca725d0a918a74f695f5e4c3f7e0c7bb25d91341832fbb789e35
Timestamp: 1648568876 Timestamp [UCT]: 2022-03-29 15:47:56 Age [y:d:h:m:s]: 02:314:19:43:49
Block: 468986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744339 RingCT/type: yes/0
Extra: 01fa02cb78f582ca725d0a918a74f695f5e4c3f7e0c7bb25d91341832fbb789e3502110000000c06faf294000000000000000000

1 output(s) for total of 17.141741737000 dcy

stealth address amount amount idx
00: 7672b9e84d319981f7fa2911c59fce1bbbbbab0c16444c84d33a87571e7b8147 17.141741737000 887824 of 0

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": 468996, "vin": [ { "gen": { "height": 468986 } } ], "vout": [ { "amount": 17141741737, "target": { "key": "7672b9e84d319981f7fa2911c59fce1bbbbbab0c16444c84d33a87571e7b8147" } } ], "extra": [ 1, 250, 2, 203, 120, 245, 130, 202, 114, 93, 10, 145, 138, 116, 246, 149, 245, 228, 195, 247, 224, 199, 187, 37, 217, 19, 65, 131, 47, 187, 120, 158, 53, 2, 17, 0, 0, 0, 12, 6, 250, 242, 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