Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442cf8ec01c4122e27c42adc19944812636e0a1f40808e1ed0b242018134a6b5

Tx prefix hash: 121905f79c2be5481df77c5f2ab8d1431078980ce50cdd2cab83306b9c3b5162
Tx public key: 81d8b958f04222304a97581a8a9bb82baa329be2184c12bbe8262e9ae9891e54
Timestamp: 1631756011 Timestamp [UCT]: 2021-09-16 01:33:31 Age [y:d:h:m:s]: 03:171:00:40:55
Block: 334665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 897704 RingCT/type: yes/0
Extra: 0181d8b958f04222304a97581a8a9bb82baa329be2184c12bbe8262e9ae9891e540211000000138d0de867000000000000000000

1 output(s) for total of 47.765724416000 dcy

stealth address amount amount idx
00: 0d16ab251c9c6a37246a5d0db84bc383bad4c59f169a01eae506d5bd0a40b161 47.765724416000 690192 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": 334675, "vin": [ { "gen": { "height": 334665 } } ], "vout": [ { "amount": 47765724416, "target": { "key": "0d16ab251c9c6a37246a5d0db84bc383bad4c59f169a01eae506d5bd0a40b161" } } ], "extra": [ 1, 129, 216, 185, 88, 240, 66, 34, 48, 74, 151, 88, 26, 138, 155, 184, 43, 170, 50, 155, 226, 24, 76, 18, 187, 232, 38, 46, 154, 233, 137, 30, 84, 2, 17, 0, 0, 0, 19, 141, 13, 232, 103, 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