Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec03704fb8215e7338d1e41490a2ff1bc75358dea0d920e6f86c0afa77b70577

Tx prefix hash: 174491e0c67611dd85c16503665b460f833b45fc6daa84df5abdd08c796150f3
Tx public key: 0beba0eb69e6250cf5c85c54ee409d1eb976e82a5e28adf768c781aaa8e96072
Timestamp: 1582445008 Timestamp [UCT]: 2020-02-23 08:03:28 Age [y:d:h:m:s]: 05:229:05:33:17
Block: 70875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1314602 RingCT/type: yes/0
Extra: 010beba0eb69e6250cf5c85c54ee409d1eb976e82a5e28adf768c781aaa8e96072021100000002724f989b000000000000000000

1 output(s) for total of 357.406548731000 dcy

stealth address amount amount idx
00: 1ebca33e18af755eeb4c93f82df7eb1a42aa9d17fbf8a20f7df1eb56b71e0d14 357.406548731000 130921 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": 70885, "vin": [ { "gen": { "height": 70875 } } ], "vout": [ { "amount": 357406548731, "target": { "key": "1ebca33e18af755eeb4c93f82df7eb1a42aa9d17fbf8a20f7df1eb56b71e0d14" } } ], "extra": [ 1, 11, 235, 160, 235, 105, 230, 37, 12, 245, 200, 92, 84, 238, 64, 157, 30, 185, 118, 232, 42, 94, 40, 173, 247, 104, 199, 129, 170, 168, 233, 96, 114, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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