Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3792a9fd9605a22a6be8bbcfc75803520743cea85e3d402de07463093892556b

Tx prefix hash: 0746b822ca2efc27ce965ec43a903486c25676d747b8e06e5e79b0cbbbf83dbe
Tx public key: e4d4345f15525efeb012d804d15cd46594497094d39a031c2e28caf08ca730a4
Timestamp: 1587536202 Timestamp [UCT]: 2020-04-22 06:16:42 Age [y:d:h:m:s]: 04:252:01:42:33
Block: 94934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090648 RingCT/type: yes/0
Extra: 01e4d4345f15525efeb012d804d15cd46594497094d39a031c2e28caf08ca730a402110000001c209b4bc8000000000000000000

1 output(s) for total of 297.471262966000 dcy

stealth address amount amount idx
00: 46a67d95f4b1f5fd9effdd47972a5096680bcff3c64a2e1cf11b1896f1b9f797 297.471262966000 168814 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": 94944, "vin": [ { "gen": { "height": 94934 } } ], "vout": [ { "amount": 297471262966, "target": { "key": "46a67d95f4b1f5fd9effdd47972a5096680bcff3c64a2e1cf11b1896f1b9f797" } } ], "extra": [ 1, 228, 212, 52, 95, 21, 82, 94, 254, 176, 18, 216, 4, 209, 92, 212, 101, 148, 73, 112, 148, 211, 154, 3, 28, 46, 40, 202, 240, 140, 167, 48, 164, 2, 17, 0, 0, 0, 28, 32, 155, 75, 200, 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