Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abbfc42e72128f7fbfc754b600976f71f434041f632f45ef85d15c6b695ed618

Tx prefix hash: 2cba3ba96bc628c0ff106df3ecd6841a7b1393b59624dd8149d3566aaa9f4957
Tx public key: 64d714b8b6381b51794922a3c67e19b08c4dd1d430a4f090683c5cbbd42cf080
Timestamp: 1704476915 Timestamp [UCT]: 2024-01-05 17:48:35 Age [y:d:h:m:s]: 01:331:08:38:08
Block: 928844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495687 RingCT/type: yes/0
Extra: 0164d714b8b6381b51794922a3c67e19b08c4dd1d430a4f090683c5cbbd42cf08002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c00c630add40576966918ffcd09f18aaac4904132b8bf4dc10bc0d1b2fdec14 0.600000000000 1386708 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": 928854, "vin": [ { "gen": { "height": 928844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c00c630add40576966918ffcd09f18aaac4904132b8bf4dc10bc0d1b2fdec14" } } ], "extra": [ 1, 100, 215, 20, 184, 182, 56, 27, 81, 121, 73, 34, 163, 198, 126, 25, 176, 140, 77, 209, 212, 48, 164, 240, 144, 104, 60, 92, 187, 212, 44, 240, 128, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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