Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fca57bb3b7c915ed998cf809698938f09da6473c05236621f95b9285728a4e0f

Tx prefix hash: 570c297bf341eeab99f1807e99340bb368504004225c2c9bfe8127e332d97eef
Tx public key: f46531de49f08994a2e2dfce9b8d7f8a5dddc84d2a1c502d961f9bd00a2c79c5
Timestamp: 1639477066 Timestamp [UCT]: 2021-12-14 10:17:46 Age [y:d:h:m:s]: 03:054:19:57:09
Block: 395270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 817898 RingCT/type: yes/0
Extra: 01f46531de49f08994a2e2dfce9b8d7f8a5dddc84d2a1c502d961f9bd00a2c79c5021100000003eaa12622000000000000000000

1 output(s) for total of 30.082003952000 dcy

stealth address amount amount idx
00: bb48d40ed34a10eae92e8f4aabe1cda9107055039ee918c4a37bdf3161304a73 30.082003952000 793131 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": 395280, "vin": [ { "gen": { "height": 395270 } } ], "vout": [ { "amount": 30082003952, "target": { "key": "bb48d40ed34a10eae92e8f4aabe1cda9107055039ee918c4a37bdf3161304a73" } } ], "extra": [ 1, 244, 101, 49, 222, 73, 240, 137, 148, 162, 226, 223, 206, 155, 141, 127, 138, 93, 221, 200, 77, 42, 28, 80, 45, 150, 31, 155, 208, 10, 44, 121, 197, 2, 17, 0, 0, 0, 3, 234, 161, 38, 34, 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