Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47b5ab47628b74a20f1f27c5935ab7a1abd2b560e3249dd2f3c79a1a5cc275f8

Tx prefix hash: c41f42d96aef68d681cca09ed0be6af61ef4f912de64704b0e0c142f97527769
Tx public key: 17060a18e2459fb69bd8bf112f1be493a0e855e7a9961a24c936193f36a74136
Timestamp: 1712369470 Timestamp [UCT]: 2024-04-06 02:11:10 Age [y:d:h:m:s]: 01:001:11:13:47
Block: 994261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262026 RingCT/type: yes/0
Extra: 0117060a18e2459fb69bd8bf112f1be493a0e855e7a9961a24c936193f36a7413602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d4292c3c382b1b8d1df235cd26fc0c1dedc0b04fb1134486883945ba46d012 0.600000000000 1454663 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": 994271, "vin": [ { "gen": { "height": 994261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d4292c3c382b1b8d1df235cd26fc0c1dedc0b04fb1134486883945ba46d012" } } ], "extra": [ 1, 23, 6, 10, 24, 226, 69, 159, 182, 155, 216, 191, 17, 47, 27, 228, 147, 160, 232, 85, 231, 169, 150, 26, 36, 201, 54, 25, 63, 54, 167, 65, 54, 2, 17, 0, 0, 0, 2, 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