Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca14fd158c6eeddbe47f6f532edf53d4eeb30bbcd6b896926aac2529c1e6d5cf

Tx prefix hash: 79ef85ee746f615b09f34d98c63f3c0c1e4d3922929b9cd9c33083006a3bf755
Tx public key: 45fafc073247ea6878caaa086856e95ff4a3aa3d19b147584cbacc236260b0f1
Timestamp: 1672468453 Timestamp [UCT]: 2022-12-31 06:34:13 Age [y:d:h:m:s]: 02:019:06:31:32
Block: 664356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535710 RingCT/type: yes/0
Extra: 0145fafc073247ea6878caaa086856e95ff4a3aa3d19b147584cbacc236260b0f1021100000002e7ace25d000000000000000000

1 output(s) for total of 3.861115118000 dcy

stealth address amount amount idx
00: b1910fb700b2092aed9d6778ffc639869abaeb28cf76a670702f8c97776c8783 3.861115118000 1105331 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": 664366, "vin": [ { "gen": { "height": 664356 } } ], "vout": [ { "amount": 3861115118, "target": { "key": "b1910fb700b2092aed9d6778ffc639869abaeb28cf76a670702f8c97776c8783" } } ], "extra": [ 1, 69, 250, 252, 7, 50, 71, 234, 104, 120, 202, 170, 8, 104, 86, 233, 95, 244, 163, 170, 61, 25, 177, 71, 88, 76, 186, 204, 35, 98, 96, 176, 241, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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