Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ac14220fe7d7b8ab3cf476fc19d11208c54dacaa824f3a3404b5e416d864a81

Tx prefix hash: bb37d1dad815114012d7a9b2dd12055d8ab66d6ca01cbd76fd2b7fe689c75fb4
Tx public key: d0a3493eaa61a91b521e7fba758371dae5c698752c71e5b70c1af8aedc36d2e6
Timestamp: 1656296337 Timestamp [UCT]: 2022-06-27 02:18:57 Age [y:d:h:m:s]: 02:264:08:51:41
Block: 531179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 710053 RingCT/type: yes/0
Extra: 01d0a3493eaa61a91b521e7fba758371dae5c698752c71e5b70c1af8aedc36d2e602110000000275e3f0e9000000000000000000

1 output(s) for total of 10.665559183000 dcy

stealth address amount amount idx
00: bd4ee85a2b84d96850462511809f2fec111c0b6644ef901c3e41f8403fac75c9 10.665559183000 960296 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": 531189, "vin": [ { "gen": { "height": 531179 } } ], "vout": [ { "amount": 10665559183, "target": { "key": "bd4ee85a2b84d96850462511809f2fec111c0b6644ef901c3e41f8403fac75c9" } } ], "extra": [ 1, 208, 163, 73, 62, 170, 97, 169, 27, 82, 30, 127, 186, 117, 131, 113, 218, 229, 198, 152, 117, 44, 113, 229, 183, 12, 26, 248, 174, 220, 54, 210, 230, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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